Description

Fix various minor bugs in vulnerability policy evaluation:

• Determining whether a field needs to be loaded from the database failed for Protobuf fields which are repeated and non-empty
• Converting VulnerabilityAliases to policy Protobufs failed because alias objects were not detached from the persistence context
• Synchronized VulnerabilityAliases did not end up getting passed to the policy evaluator, which in case a policy tried to access aliases triggered, necessitated a database query to load them prior to evaluation

I also refactored VulnerabilityScanResultProcessorTest to use an actual VulnerabilityPolicyEvaluator instead of a mocked one. Mocking it made it impossible to test the end-to-end process properly.

Addressed Issue

N/A

Additional Details

N/A

Checklist

• I have read and understand the contributing guidelines
• This PR fixes a defect, and I have provided tests to verify that the fix is effective
• This PR implements an enhancement, and I have provided tests to verify that it works as intended
• This PR introduces changes to the database model, and I have added corresponding update logic
• This PR introduces new or alters existing behavior, and I have updated the documentation accordingly